feat(docker): add Docker image publishing to GHCR#1820
Closed
cdelgehier wants to merge 1 commit intocommitizen-tools:masterfrom
Closed
feat(docker): add Docker image publishing to GHCR#1820cdelgehier wants to merge 1 commit intocommitizen-tools:masterfrom
cdelgehier wants to merge 1 commit intocommitizen-tools:masterfrom
Conversation
github-actions
bot
added
pr-status: wait-for-review
type: documentation
type: feature
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #1820 +/- ##
=======================================
Coverage 97.96% 97.96%
=======================================
Files 60 60
Lines 2648 2648
=======================================
Hits 2594 2594
Misses 54 54 ☔ View full report in Codecov by Sentry. |
cdelgehier
force-pushed
the
feat/build-push-action
branch
from
5f725ca to
7bbe85f
Compare
This implementation adds automated Docker image publishing to GitHub Container Registry (ghcr.io) on every release tag. - [x] I have read the [contributing guidelines](https://commitizen-tools.github.io/commitizen/contributing/) - [ ] Add test cases to all the changes you introduce - [ ] Run `uv run poe all` locally to ensure this change passes linter check and tests - [x] Manually test the changes: - [x] Verify the feature/bug fix works as expected in real-world scenarios - [ ] Test edge cases and error conditions - [ ] Ensure backward compatibility is maintained - [x] Document any manual testing steps performed - [x] Update the documentation for the changes - [x] Run `uv run poe doc` locally to ensure the documentation pages renders correctly - [x] Check and fix any broken links (internal or external) in the documentation > When running `uv run poe doc`, any broken internal documentation links will be reported in the console output like this: > > ```text > INFO - Doc file 'config.md' contains a link 'commands/bump.md#-post_bump_hooks', but the doc 'commands/bump.md' does not contain an anchor '#-post_bump_hooks'. > ``` <!-- A clear and concise description of what you expected to happen --> The Docker image will be published at: ghcr.io/commitizen-tools/commitizen <!-- Steps to reproduce the behavior: 1. ... 2. ... 3. ... --> <!-- Add any other RELATED ISSUE, context or screenshots about the pull request here. --> Key features: - Multi-stage Dockerfile using Python 3.13 slim and UV - GitHub Actions workflow for automated publishing on v* tags - Multi-architecture support (amd64, arm64) - Multiple image tags (latest, version, major.minor, major, sha) - Build attestation for supply chain security - Documentation: new Docker tutorial and updates to existing CI guides
cdelgehier
force-pushed
the
feat/build-push-action
branch
from
7bbe85f to
544c521
Compare
Member
|
Hi there, thanks for the intention, but we already have a docker repository, would you mind sending a PR there? 🙏🏻 |
Author
|
Hi @woile ! Thanks for your response.
|
Member
|
We can always trigger the job from here towards there once a release happen using 
If you update the |
Author
|
Drafted here |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This implementation adds automated Docker image publishing to GitHub Container Registry (ghcr.io) on every release tag.
-
-
-
-
- Verify the feature/bug fix works as expected in real-world scenarios
- Test edge cases and error conditions
- Ensure backward compatibility is maintained
- Document any manual testing steps performed
-
-
-
The Docker image will be published at: ghcr.io/commitizen-tools/commitizenI have read the contributing guidelines
Add test cases to all the changes you introduce
Run
uv run poe alllocally to ensure this change passes linter check and testsManually test the changes:
Update the documentation for the changes
Run
uv run poe doclocally to ensure the documentation pages renders correctlyCheck and fix any broken links (internal or external) in the documentation
Key features: